Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Merging approved edits into master #33

Closed
wants to merge 30 commits into from
Closed

Merging approved edits into master #33

wants to merge 30 commits into from

Conversation

jasnell
Copy link
Collaborator

@jasnell jasnell commented Oct 15, 2014

No description provided.

jasnell and others added 30 commits August 1, 2014 10:53
vocabulary definition to the activitystream2-vocabulary document, begin
extracting out the best practices information to a separate document.
- And a tweak on one of the example descriptions
objects. Specifically:
 - Define the relationship between "id", "url", "self", "alternate" and
other types of links
 - Define some best practices for consistent / interoperable use of
links
 - Define url as being an IRI/URI only, not a Link Value
could... existing JSON-LD parsers do not handle it well
"as:result". Used to indicate the activity for which the object or link
is a result. See
#20
these to the vocab just yet tho... they're just in the @context
#24 (comment)
omment-58074056

This does several things:

1. It outlines a clearer separation between as:Object and as:Link
2. It models as:Link in much the same way that hydra:Link is defined,
using it as a marker to indicate that the @id is dereferencable
3. It specifically handles the case where a JSON-LD object is defined
as both an Object and a Link (e.g. "@type": ["as:Link",
"urn:foo:object"])

For anyone looking at this without JSON-LD glasses on, this might look
strange, but it works. Compatibility with AS 1.0 is preserved and
people who want to use the JSON only model (without the additional -LD
stuff) can continue to do so without any additional complication.
and verb blank nodes
2. Fix Pat Cappelaere's name in the acknowledgements per his request
3. Adding W3C basic geo and geosparql to initial context
 - trailing "f" in a json example
 - "widht" => "width"
 - Add > after James Snell's email address
@jasnell jasnell closed this Oct 15, 2014
@jasnell jasnell deleted the gh-pages branch October 15, 2014 16:34
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Projects
None yet
Development

Successfully merging this pull request may close these issues.

None yet

3 participants